Bump the hl7-fhir group with 1 update - #5860
Closed
dependabot[bot] wants to merge 1 commit into
Closed
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps Hl7.Fhir.Base from 5.11.4 to 6.5.0 --- updated-dependencies: - dependency-name: Hl7.Fhir.Base dependency-version: 6.5.0 dependency-type: direct:production update-type: version-update:semver-major dependency-group: hl7-fhir ... Signed-off-by: dependabot[bot] <support@github.com>
|
Azure Pipelines: There may be pipelines that require an authorized user to comment /azp run to run. |
Contributor
Author
|
Superseded by #5861. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updated Hl7.Fhir.Base from 5.11.4 to 6.5.0.
Release notes
Sourced from Hl7.Fhir.Base's releases.
6.5.0
Intro:
This release is mostly about the cost of parsing and serializing: allocations on the hot path of
(de)serialization are down substantially, and the serializers no longer emit empty objects or
elements. It also collects a series of
SnapshotGeneratorfixes and a concurrency fix interminology validation. There are no breaking API changes, but two
SnapshotGeneratorOperationOutcomeissue codes were renumbered to remove duplicates (10012 -> 10018,10014 -> 10019), which affects code that switches on those numbers. See the behavioural
notes below.
Serialization
{}) or empty elements (<x/>). A structure isopened only once it is known to have content, so an empty POCO - or one emptied out by a
SerializationFilter, as happens when summarizing - no longer produces output our owndeserializer rejects with
OBJECTS_CANNOT_BE_EMPTY/ELEMENT_CANNOT_BE_EMPTY. Summarizedresources now round-trip. See issue #3557.
NOOVERFLOWpreset, next toSTRICT.DeserializationMode.NoOverflowwas the one mode without a preset, reachable only by constructing the settings by hand. Thanks to
@sujeito-operator for the contribution. See issue #3532.
new FhirUri((Uri)null)no longer throws aNullReferenceException;FhirUrl(Uri)andCanonical(Uri)had the same problem. They now null-propagate, like the other primitivedatatype constructors. See issue #3578.
Performance
produced by model validation - which runs on every element in every deserialization mode except
SyntaxOnlyandOstrich- rather than the POCO graph it returns. Validation now allocates abouthalf of what it did, and the validation outcomes are unchanged. Measured on a Patient
StructureDefinition (88 KB): 5.1 MB allocated and 3.4 ms per parse, down to 2.5 MB and 1.8 ms.
With the validator off, the same parse went from 1.4 MB to 1.0 MB.
ClassMappinghot path no longer allocates per access. Two patterns - aLazyInitializerfactory allocated on every call, including the warm path, and a full locked snapshot of the
property mapping collection - sat on the per-element path of every (de)serialization and are now
gone.
on .NET 10 and later (
ClassMappingCollection.FindByName(ReadOnlySpan<char>)), with a fallbackon earlier frameworks.
Snapshot generation
NotSupportedException("Can only jump to local nameReferences") when a differentialelement carried a complex type profile reference of the form
canonicalUrl#elementNameandhad child constraints. See issue #3583.
Base- which is only a resolvableStructureDefinitionfrom R5 onwards - are now handled gracefully. Before R5,
Baseis treated as an empty root and awarning is emitted instead of the generator failing. Element matching and child handling for
anonymous and untyped logical model elements were improved along with it (VONK-10132).
OperationOutcomeissue codes were each used for two unrelated conditions. The duplicateshave been resolved:
PROFILE_ELEMENTDEF_SLICENAME_NOMATCHmoves from 10012 to 10018, andPROFILE_STRUCTURE_TYPE_MISSINGmoves from 10014 to 10019. Code that switches on thesenumeric codes needs updating. See issue #3587.
... (truncated)
6.4.0
Intro:
This release adds opt-in retention of XML comments in the POCO-based parser. There are no breaking changes.
Serialization
The POCO-based XML parser can now retain the comments found in the source document. Set
DeserializerSettings.RetainCommentstotrue(the default remainsfalse) and comments are attached to the parsed POCOs asSourceCommentsannotations, so that they survive a parse/serialize round-trip. See issue #3561.Dependencies
Changes:
This list of changes was auto generated.
6.3.0
Intro:
This release includes a behavioral change in parsing alongside a minor bug fix. Please read the notes below carefully before upgrading.
POCO / type system
The SDK now detects incorrectly cased element and resource type names. Two new error codes are introduced:
PVAL131(WRONG_CASED_ELEMENT) andPVAL132(WRONG_CASED_RESOURCE_TYPE).Other fixes
Changes:
setLinkmethodThis list of changes was auto generated.
6.2.1
Intro:
This is a bugfix release with several stability and correctness improvements.
Serialization
OverflowExceptionwhen serializing large decimal values with old parsing stackFhirClientto use the modern POCO serializer for better consistencySettings.SerializationEnginean instance ofFhirSerializationEngineFactory.Legacy.FromParserSettings(ModelInfo.ModelInspector, Settings.ParserSettings ?? new())as it was beforeprettyoption being ignored when callingToXml()Snapshot generation
POCO / type system
ISourceNodenow has a directToPoco()extension methodinstantvalues being stored incorrectly when converting from an untyped sourceClassMappingforModelInspectorParametersclassIVersionableConformanceResourceto R5NamingSystemOther fixes
null, leaving it to the caller to decide whether to throwChanges:
See More
... (truncated)
6.2.0
Intro:
RespectSuppressExtensionsetting toSnapshotGeneratorSettings(default:true) to allow consumers to opt out of suppress-extension handling during snapshot generation.Base.ClearOverflow()and corrected theNoOverflowdocstring.ITypedElementextension methods now useOverloadResolutionPriority(1), ensuring they are preferred overISourceNodeextensions for types implementing both interfaces (such asPocoNode).CachingTerminologyServicewhere resource or unrecognized parameter values could produce invalid cache keys.System.Text.JsonandMicrosoft.Extensions.Caching.Memoryto version10.0.7.Changes:
See More
This list of changes was auto generated.
6.1.1
Intro:
Fixes wrong logic for BaseTerminologyService filtering parameters for duplicates on requests that accept 0..* on some parameters
Changes:
This list of changes was auto generated.
6.1.0
Intro:
FHIRPathCompiledExpressionnow accepts0..*resources as input, removing the need for a dummy resource when the expression does not reference one.ModelInspectornow protects against cross-version contamination ofClassMappings, preventing type resolution errors when multiple library versions are used in the same process.MemberNameproperty for easier debugging.Changes:
See More
This list of changes was auto generated.
6.0.2
Intro:
Mostly minor changes, but one breaking change where the PocoNode's ParentNode constructor has been removed, as it was not
necessary and is derived from the Parent.
Changes:
See More
This list of changes was auto generated.
6.0.1
Intro:
Fixes Code having System and Value switched.
Leaves snapshot generation result usability to the caller rather than assuming error.
Changes:
This list of changes was auto generated.
6.0.0
Intro:
Firely .NET SDK v6.0.0
Changes:
... (truncated)
6.0.0-rc1
Intro:
Firely .NET SDK v6.0.0 release candidate 1
Changes:
See More
This list of changes was auto generated.
6.0.0-beta1
Intro:
Firely SDK 6.0.0-beta1
Changes:
See More
... (truncated)
6.0.0-alpha2
Intro:
Firely SDK 6.0.0-alpha2
Changes:
See More
This list of changes was auto generated.
6.0.0-alpha1
Introducing Firely SDK 6
SDK 6.0 is a major release putting the POCOs more and more at the center of our development efforts. We are extending the POCOs to be more flexible and the interface between POCOs and the FhirPath engine (and validation) to be more performant. This is our plan to make this a reality:
This will almost completely remove the dependency on the ITypedElement stack from our POCOs and FP/validation, resulting in more performance and less memory use. At the same time we strive to keep the current ITypedElement-based code working for the forseeable future.
This early alpha is really an internal release, so unfortunately there is no documentation available on the new features, and it is likely the new APIs will change based on the feedback we get from testing this alpha in our Firely products. That said, we expect this 6.0 to be mostly backwards-compatible, so you CAN definitely try to update to this release and see if your software still works. We'd love to learn about any regressions you might encounter.
Changes:
See More
IScopedNodeexplicitly on POCO's... (truncated)
5.13.4
Intro:
Restored lazy-initialization pattern on the ModelInspector.
Changes:
ModelInspectorThis list of changes was auto generated.
5.13.3
Intro:
Restored the ModelInspector caching behavior removed in previous version.
We diagnosed the underlying issue, and will now throw a runtime exception in cases where the cross ClassMapping import would occur.
Changes:
See More
This list of changes was auto generated.
5.13.2
Intro:
Reverts the caching of ModelInfo.ModelInspector due to issues with cross version codes importing and overriding type mappings.
Changes:
This list of changes was auto generated.
5.13.1
Intro:
Fixed ValueSet serialization being not resistant to unknown elements.
Improve cleaning up of extensions that should not be inherited during snapshot generation.
Changes:
See More
This list of changes was auto generated.
5.13.0
Intro:
Added support for not trimming whitespace in serialization
Made minor changes to the snapshot generator
Changes:
This list of changes was auto generated.
5.12.2
Intro:
Added FHIRPath debug tracer.
Fixes bugs related to paralelization when using SerializationFilter.
Optimization tweaks.
Changes:
This list of changes was auto generated.
5.12.1
What's Changed
Full Changelog: FirelyTeam/firely-net-sdk@v5.12.0...v5.12.1
5.12.0
Intro:
Added an FHIR R6-ballot3 sattelite and Nuget package.
Changes:
This list of changes was auto generated.
5.11.7
Intro:
A hotfix that prevents issues when
BundledResourcesis called when any of the bundle entries missesfullUrlChanges:
This list of changes was auto generated.
5.11.6
Intro:
A hotfix for a bug causing resolving to fail on local bundle references
Changes:
This list of changes was auto generated.
5.11.5
What's Changed
New Contributors
Full Changelog: FirelyTeam/firely-net-sdk@v5.11.4...v5.11.5
Commits viewable in compare view.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions